| Aspect | Description |
|---|---|
|
Vendor
|
GSX 365 |
|
Details
|
Website |
|
Term
|
Technical Monitoring |
|
Purpose/
Statement
|
Sale/ Provide Information |
|
Genre/
Research Methods
|
Descriptive website |
|
Concept
|
Technical Monitoring |
|
IT involved
|
Dashboard |
|
Data Sources
|
Sensors ("robots") |
|
(Research)
Methods
|
Sensors deployed to each location that access endpoints and simulate user activity; then visualise & analyse results |
|
Stakeholders
|
IT managers & System Admins |
|
Goals
|
Anticipate and decrease technical performance issues (latency, uptime, routing) and reduce time2repair |
|
Theoretical
Warrant(s)
|
Not clear |
|
Level of Analysis
|
Technical components |
|
Side effects
|
None |
|
Theoretical instantiation/ link function
|
None |
|
Comparison with our model
|
This is a more technical tool. Which monitors the behavior of the tools (skype for business, Yammer, office 365 in general) to detect issues before those can affect employees. |
|
Comment
|
technical tool; maybe we should skip this? It is unrelated to people analytics, except it connects to O365 |